fix: remove duplicate CI pipeline on push to main#12
Conversation
ci.yml and main-ci.yml both triggered on push to main with identical CI steps, causing every merge to run the full suite twice. main-ci.yml already covers all CI checks plus release handling, making ci.yml entirely redundant. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Gemini AI Code ReviewIssues (if any)(none) Previous Issues (for incremental reviews)(none) Suggestions (if any)(none) Notes
Generated by Gemini AI (gemini-3-flash-preview). Supplementary to human reviews. |
Codex AI Code ReviewIssues (if any)(none) Previous Issues (for incremental reviews)(none) Suggestions (if any)(none) Notes
Generated by Codex AI (gpt-5.3-codex). Supplementary to human reviews. |
Review Response Agent (Iteration 1)Status: No changes needed Fixed Issues
Ignored Issues
Deferred to Human
Notes
The agent reviewed feedback but determined no code changes were required. |
Summary
.github/workflows/ci.yml-- this workflow triggered onpush: branches: [main]with the exact same CI steps asmain-ci.yml, causing every merge to main to run the full CI suite twiceCLAUDE.mdto reflect the remaining two workflows instead of threemain-ci.ymlalready handles all CI checks (fmt, clippy, test, build, deny, emulator) plus release binary creation and GitHub Release on tags/manual trigger --ci.ymlwas entirely redundantTest plan
main-ci.ymlstill runs on push to main (triggers section unchanged)pr-validation.ymlstill runs on PR open/sync/reopen (untouched)Generated with Claude Code